Configuring SNMP for OVOC Connectivity

Connection between the device and OVOC is through SNMP. Once connected, the device can send SNMP traps to OVOC, and OVOC can perform various operations on the device such as maintenance actions, and fault and performance management.

● Make sure that the SNMP settings on the device and on OVOC are identical.
● OVOC uses the following default settings:
✔ Trap port: 162 (configured in the SNMP Trap Destinations table, as described below).
✔ SNMPv2: public for the read-community string, private for read-write community string, and trapuser for the trap community string (configured on the SNMP Community Settings page, as described below).
✔ SNMPv3: OVOCUser for user name; SHA-1 for authentication protocol; AES-128 for privacy protocol; 123456789 for the 'Authentication Key' and 'Privacy Key' password (configured in the SNMPv3 Users table, as described below).
● If the device is located behind NAT and you have added it to OVOC by serial number or by auto-detection, you also need to configure (through ini file) the device to send NAT keep-alive traps to the OVOC port to keep the NAT pinhole open for SNMP messages sent from OVOC to the device:
✔ [SendKeepAliveTrap] = [1]
✔ [KeepAliveTrapPort] = [1161]
✔ [NatBindingDefaultTimeout] = [30]
➢ To configure SNMP for device-OVOC connectivity:
1. Make sure that SNMP is enabled, which it is by default (see Enabling or Disabling SNMP).
2. Configure the local SNMP port (for Get/Set commands) on the device to 161, using the [SNMPPort] parameter.
3. Configure an SNMPv2 or SNMPv3 user:
● For SNMPv2 user:
i. Open the SNMP Community Settings page (Configuring SNMP Community Strings).
ii. In the 'Read-Only 1' parameter [SNMPReadCommunity), configure the SNMP read-only community string.
iii. In the 'Read-Write 1' parameter [SNMPWriteCommunity], configure the SNMP read-write community string.
iv. In the 'Trap Community String' parameter [SNMPTrapCommunityStringPassword], configure the community string for SNMP traps.
● For SNMPv3 users:
i. Open the SNMPv3 Users table (see Configuring SNMPv3 Users).
ii. In the 'User Name' parameter, configure the name of the SNMPv3 user.
iii. From the 'Authentication Protocol' drop-down list, select the authentication protocol.
iv. From the ’Privacy Protocol' drop-down list, select the privacy protocol.
v. In the 'Authentication Key' and 'Privacy Key' parameters, configure the password.
4. Configure the device to send its traps to OVOC (acting as an SNMP Manager), in the SNMP Trap Destinations table (see Configuring SNMP Trap Destinations with IP Addresses):
a. In the 'IP Address' parameter, configure the OVOC IP address.
b. In the 'Trap Port' parameter, configure the OVOC port.
c. From the 'Trap User' drop-down list, select a trap user (SNMPv2 or SNMPv3) for this trap destination.
d. From the 'Trap Enable' drop-down list, select Enable.

Below shows an example where OVOC is configured as an SNMP Manager with IP address:port 172.17.118.219:162 and using an SNMPv3 user:

If the OVOC address is an FQDN, instead of configuring the SNMP Manager (OVOC) above with an IP address in dotted-decimal notation, you can configure a single SNMP trap manager with an FQDN, as described in Configuring an SNMP Trap Destination with FQDN.

5. If the device is located behind NAT and you have added the device to OVOC by its serial number or using auto-detection, you also need to configure (through ini file) the device to send NAT keep-alive traps to the OVOC port to keep the NAT pinhole open for SNMP messages sent from OVOC to the device:
a. Enable the sending of NAT keep-alive traps to OVOC, by configuring the [SendKeepAliveTrap] parameter to [1].
b. Define the OVOC port to where the device sends the NAT keep-alive traps, by using the [KeepAliveTrapPort] parameter.
c. Define the interval between each sent NAT keep-alive trap, by using the [NatBindingDefaultTimeout] parameter.
6. Restart the device with a save-to-flash for your settings to take effect.